Method for displaying web user&#39;s authentication status in a distributed single login network

ABSTRACT

The invention provides a system and method for automatically displaying a user&#39;s logged-in status across an Internet based network of affiliated Web sites via a visual indicator such as a toolbar to help the user to be certain about his logged-in status when he stays with one or switches from one to another affiliated Web site.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.10/365,979, filed Feb. 12, 2003 now U.S. Pat. No. 7,305,470.

BACKGROUND OF THE INVENTION

1. Technical Field

This invention relates generally to cross domain authenticationtechnology. More particularly, the invention relates to a method andsystem for automatically displaying a Web user's authentication statusacross an Internet based network of participating Web sites.

2. Description of the Prior Art

To request a service or conduct other electronic transactions in anInternet based network, a user is usually required to go through anauthentication process. In other words, the user is required to providethe seller or service provider with some credential information, such ashis personal identification, contact information, or even financialinformation. The authentication process may take from several seconds toseveral minutes. Because each seller or service provider usuallymaintains its own authentication server and database, millions ofsellers and service providers might share thousands or millions ofconsumers or users. Some of the consumers or users might be required togo through the same or substantially similar authentication processagain and again if they have transactions with many sellers or serviceproviders. This repetitive authentication not only wastes the consumers'time, but also burdens the sellers or service providers because theyhave to expand their databases to keep detailed authenticationinformation for a growing number of users. This situation brings forth atechnical need to create a universal, unified, single-logininfrastructure wherein a specific user may be authenticated once for alland the authentication result is widely recognized by a large number ofsellers or service providers.

In responding to that need, several approaches have been developed. Forexample, Microsoft Corporation has introduced a “.NET Passport” singlesign-in system. With “.NET Passport,” a user does not need to register amember name and password at each affiliated site he visits. The user maysimply use his e-mail address and password that registered as his “.NETPassport” to sign in to any participating site of the network. Theinformation the user registers with “.NET Passport” is stored online,securely, in the “.NET Passport” database as the user's “.NET Passportprofile.” When the user signs in to a “.NET Passport” participating siteby typing his e-mail address and password in the “.NET Passport” sign-inbox, “.NET Passport” confirms that (1) the e-mail address he entered isregistered with “.NET Passport”, and (2) the password he entered iscorrect. “.NET Passport” then notifies the site that the user hasprovided valid “sign-in credentials,” and thus he is given access to theparticipating site. Once the user signs in to one “.NET Passport”participating site during an Internet session, he can sign in to anyother site simply by clicking the “.NET Passport” sign-in buttonavailable at the site.

Another example is America Online Incorporated (AOL)'s “Screen NameService” system, which provides a free service allowing anyone with a“Screen Name” to register easily and securely at a variety of Web sites.The “Screen Name Service” eliminates a user's need to remember multiplenames and passwords for all the places he visits on the Web. With the“Screen Name Service” system, each user has a “My Profile”, which storesthe user's personal credentials used to make registration at sitesacross the Web simple and secure. When the user registers at aparticipating site using the service, he has the opportunity to choosewhich fields of information stored by AOL, if any, he would like toshare with that site. No information is shared with any site without theuser's explicit permission. When the user agrees to share certaininformation with a participating site, that information is conveyed tothe site at which he is registering. Another feature is that the user isprovided with a “My Site List”, which is an effective way to managepersonal information because it shows the user with which sites he hasregistered using the service. The user can view the privacy policy of asite to see how it uses information it knows about the user. The usercan also decide if he would like to be signed into the site withoutbeing prompted and if the site should be updated with information when“My Profile” changes.

In these distributed single login networks, cross domain status toolbarsor indicators are static and do not display a personalized greetingacross multiple domains. For example, when the user with a screen name“ljewpt9” logs in the MSN e-mail service, his full e-mail addressljewpt9@hotmail.com is displayed in the upper-left corner of every mailservice pages such as the “inbox,” “sent,” “trash,” etc. When the userswitches to other pages hosted by MSN, such as “search,” “music,”“sports,” neither the user's e-mail address, nor his screen name, norhis first name or last name associated with his account is displayed.There is only a small bar “sign Out.net” embedding in the pages. Withouta close look, the user is not certain whether he is still logged-in orwho is currently logged-in on the page. Similarly, when the userswitches from an MSN page to any other affiliated website with “.NETPassport”, the user's logged-in status or personalized greeting is notexpressly displayed in the targeted pages.

Websites, such as yahoo.com and amazon.com, display personalizedgreetings on their sites, but only on pages under the same domain fromwhich they originally authenticated. For example, a user, with a screenname “ljewpt9”, who is authenticated to yahoo.com can only be identifiedon Web pages hosted on yahoo.com. When the user logs in the yahoo e-mailservice, his full e-mail address ljewpt9@yahoo.com is displayed in theupper-right corner of every mail service pages such as the pages for“inbox”, “draft”, “sent”, “trash”, and “bulk”, etc. When the userswitches to “Yahoo! Travel” or “Weather”, a greeting like “Welcome,Ljewpt9” is displayed on the page. However, the user's login statuscannot be displayed on any other Web pages which are not hosted byyahoo.com.

What is desired is a mechanism to automatically display a user'slogged-in status across an Internet based network of affiliated Websites so that the user is certain about his logged-in status when hestays with one or switches from one to another affiliated Web site.

SUMMARY OF THE INVENTION

The invention provides a system and method for automatically displayinga user's logged-in status across an Internet based network of affiliatedWeb sites via a visual indicator such as a toolbar to help the user tobe certain about his logged-in status when he stays with one or switchesfrom one to another affiliated Web site. The visual indicator has twomodes: logged-in and logged-out. In the logged-in mode, the indicatordisplays the user's login name, such as a screen name or a personalizedgreeting, and a virtual button, by clicking which the user signs out. Inthe logged-out mode, the indicator displays a virtual button for signingin. When the user has signed in one participating site of the network,the user is automatically recognized at all other sites which use thevisual indicator.

The visual indicator is hosted on a single Web site. Once the user hasbeen authenticated to the indicator Web site, the user is recognized atall affiliated Web sites that embed the indicator. A Web site embeds theindicator by instructing the user's Web browser to load additionalJavaScript from the indicator Web site. The additional JavaScript writesthe indicator HTML onto the Web page that the user visits.

The invention allows a participating Web site to recognize a user whohas never visited the site before and customize its content based on theuser. The invention can also be used to track users across multiple Websites to determine their interests and to display customized content andpromotions targeted to the user.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram illustrating a distributed, singlelogin network according to the invention;

FIG. 2 is a schematic flow diagram illustrating a method forautomatically displaying a Web user's authentication status in adistributed single login network according to the invention;

FIG. 3 a is an exemplary page where an authentication status indicatoris in its logged-out mode;

FIG. 3 b is a schematic diagram showing a typical graphical arrangementof the status indicator in logged-out mode;

FIG. 4 is an exemplary “sign in” page where the user enters his loginname and his password for authentication;

FIG. 5 a is an exemplary page where the status indicator is in logged-inmode showing the user is validly logged in;

FIG. 5 b is a schematic diagram showing a typical graphical arrangementof the status indicator in its logged-in mode;

FIG. 6 a is an exemplary page of a participating site where the user'slogged-in status is automatically displayed in the status indicator whenthe user switches to this site;

FIG. 6 b is an exemplary schematic diagram of the status indicator inlogged-in mode with a slightly different appearance; and

FIG. 7 is a flow diagram illustrating a method for automaticallydisplaying a Web user's authentication status in a distributed singlelogin network using an authentication status cookie according to theinvention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is schematic block diagram illustrating a distributed, singlelogin network 100 which comprises at least one client 101 with a Webbrowser 102, an authentication status indication server (ASIS) 104, aplurality of participating websites such as NETSCAPE.COM 105 and CNN.COM106, communicatively coupled to the Internet 103. The ASIS 104 centrallyhosts the authentication status indicator in all affiliated sites. Theauthentication status indicator, which displays the user'sauthentication status information, may be incorporated in a dashboard ora toolbar or any other visual cue on the Web pages. The statusinformation may include the user's login name, such as his screen nameor his e-mail address or even his full name, and/or a short welcomemessage or other information. The content of the visual indicator, i.e.the user's status information is centrally served, managed, and tracked.

The participating sites embedding the status indicator do not need torun any additional software or Web server plug-ins to display theindicator. However, they must include a few lines of HTML and a smallpiece of JavaScript code, called bootstrapping code, in their pageheaders. The function of the bootstrapping code is to instruct theuser's Web browser 102 to load additional JavaScript 107 from the ASIS104 to render each participating website's status indicator in logged-inmode or logged-out mode.

All content updates are managed from one single site, i.e. the ASIS 104.The participating sites which deploy the bootstrapping codeautomatically get future revisions on the dashboard without anyadditional work.

An exemplary of the bootstrapping code is given below:

<table border=“O” cellpadding=“O” cellspacing=“O” width=“WWW”> <tr><td><script Language=“Javascript” SRC= “http://toolbar.aol.com/dashboard.twhat?dom=XXX”> </script> </td></tr> </table>

Here, WWW should be the desired width in pixels of the Dashboard and XXXshould be the site's three digit partner code.

The user's authentication status information is stored in anauthentication status cookie 108 which is sent to the ASIS 104 when theuser is logged into the network 100. The ASIS 104 checks the validity ofthe received cookie and returns JavaScript 107 to render the toolbar inlogged-in mode if the cookie is valid, or logged-out mode if the cookieis missing or invalid.

Because the authentication status cookie 108 is stored on one centralserver (ASIS 104), the cookie 108 can be shared across multipleparticipating sites if each site embeds the bootstrapping code on theirWeb pages. The cookie is bound to the ASIS 104, not to the top leveldomains such as .NETSCAPE.COM or .AOL.COM. Since the cookie 108 shouldonly be read by the ASIS 104, it should be acceptable to keep the cookiein clear text. This eliminates the computational overhead of decryptingthe cookie for each page view. Alternatively, the ASIS 104 may use otherauthentication methods without using a local status cookie.

To prevent unauthorized sites from reading the user's sensitive personaldata, the ASIS 104 never returns the user's screen name in the indicatorJavaScript or in text form. Instead, an image containing the screen nameis used and the browser 102 is instructed to display the image. Thismechanism prevents unauthorized sites from reading or extracting thescreen name or other personal information from users who visit them.

Alternatively, each website could maintain their own authenticationscheme, using cookies or some other method. A website would have no wayof determining if the user has logged into any other participatingwebsite. A system could be devised where a participating website wouldredirect the user's browser to a third party site which would thensomehow pass the authentication credentials back to the originatingsite, if the user is logged in. However, the originating site would haveto redirect all users to this third party site, without knowing ahead oftime if the user is logged in. Redirecting the user to another site tocheck the authentication status is very complicated (special softwareand protocols must be installed and agreed upon between the originatingsite and the third party site) and also adds a great deal of time neededto display the content on the originating site.

Note that the authentication status indication server (ASIS) 104 isbuilt on top of a single login service (cross sites authentication) suchas AOL's Screen Name Service (SNS). Without ASIS 104, the participatingsites of the single login service such as SNS would not be able toautomatically recognize users who are signed into a different domain viaSNS. To recognize a user who is already signed into a first site viaSNS, a second site would require the user to click on a login button.There was no way to recognize the user automatically without the user'sintervention. However, this invention allows users to be recognized andauthenticated across multiple domains. Once a user has beenauthenticated to one participating site that embeds the statusindicator, the toolbar for example, the user is recognized at all otherparticipating sites that embed the indicator.

FIG. 2 is a schematic flow diagram illustrating a method forautomatically displaying a Web user's authentication status in adistributed single login network according to the invention. The methodcomprises the steps of:

Step 201: Displaying the user's logged-in status on the page of aparticipating website from which the user logged in the network 100; and

Step 202: When the user switches from one participating website toanother participating website with a different domain, automaticallydisplaying the user's logged-in status in said another participatingwebsite without requiring any browser redirects or any additional Webapplication. No client software such as browser plug-in or specialclient application is required to be installed on the user's computer,nor is any special Web application or server software required to beinstalled on the participating site's servers.

FIG. 3 a is an exemplary page of NETSCAPE.COM where an authenticationstatus toolbar 301 is in its logged-out mode. The toolbar may be in anycolor or any shape, and may be placed anywhere in the page.

FIG. 3 b illustrates a typical graphical arrangement of the toolbar 301in logged-out mode. By clicking the “Join” button 302, a user isprompted to a registration page for joining as a member. Similarly, byclicking the “Sign in” button 303, the user will be prompted to a “signin” page for authentication.

FIG. 4 is an exemplary “sign in” page 401 of NETSCAPE.COM where the userenters his screen name “Ljewpt9” and his password “****” forauthentication.

FIG. 5 a is an exemplary page of NETSCAPE.COM where the authenticationstatus toolbar is in logged-in mode 501. The toolbar may be in any coloror any shape, and may be placed anywhere in the page.

FIG. 5 b illustrates a typical graphical arrangement of the statustoolbar in its logged-in mode 501 which comprises the user's screenname, a “My Account” button 502, which links to an account informationpage, and a “Sign out” button 502, by clicking which the user signs out.

FIG. 6 a is a sample page of CNN.COM, a participating site where theuser now visits. The user's logged-in status is automatically displayedin the status toolbar which is also in logged-in mode 601.

FIG. 6 b illustrates the status toolbar in its logged-in mode 601 whichis slightly different in size and font from the status toolbar asillustrated in FIG. 5 b. The status toolbar in logged-in mode comprisesthe user's screen name, a “My Account” button 602, which links to anaccount information page, and a “sign out” button 602, by clicking whichthe user signs out.

Note that once the user logs in any participating site, the logged-instatus is recognized at any other participating site simultaneouslywithout need to redirect the user's logged-in status from a centralserver back to the user's Web browser.

FIG. 7 is a flow diagram illustrating a method for automaticallydisplaying a Web user's authentication status in a distributed singlelogin network using a status cookie according to the invention. Themethod comprises the steps of:

Step 701: Whenever the user logs in the network 100, the authenticationstatus indication server (ASIS) 104 returns JavaScript to have theuser's Web browser load the status toolbar in logged-in mode and at thesame time creates a cookie 108 storing the user's logged-in status andsends the status cookie to the user's Web browser 102;

Step 702: Whenever the user switches from one participating website toany other participating website in a different domain, the user's Webbrowser 102 sends the cookie 108 to the ASIS 104;

Step 703: The ASIS 104 compares the received cookie with the storedcookie 108;

Step 704: If the received cookie is identical with the stored cookie108, the ASIS 104 returns JavaScript 107 to render said any otherparticipating website's toolbar in logged-in mode (see FIG. 6 a and FIG.6 b, 601); and

Step 705: If no cookie is received or the received cookie is notidentical with the stored cookie 108, the ASIS 104 returns JavaScript107 to render said any other participating website's toolbar inlogged-out mode.

The method described above allows a participating Web site to recognizea user who has never visited the site before and customize its contentbased on the user. It also allows the users to personalize their UIs andlook and feel of multiple Web sites. In addition, the method can also beused to track users across multiple Web sites to determine theirinterests and to display customized content and promotions targeted tothe user.

Although the invention is described herein with reference to thepreferred embodiment, one skilled in the art will readily appreciatethat other applications may be substituted for those set forth hereinwithout departing from the spirit and scope of the present invention.

Accordingly, the invention should only be limited by the Claims includedbelow.

1. A method for automatically displaying a Web user's authenticationstatus in a distributed single login network, comprising the steps of:displaying said user's logged-in status on a first toolbar in aparticipating website from which said user has logged in said network;and whenever said user switches from any participating website to anyother participating website in a different domain, automaticallydisplaying said user's logged-in status on another toolbar in said anyother participating website without requiring any browser redirects orany additional pre-installed application; wherein each participatingwebsite of said network embeds a small piece of JavaScript bootstrappingcode which instructs said user's Web browser to load additionalJavaScript from a central server of said network to render said eachparticipating website's toolbar in logged-in state or logged-out state.2. The method of claim 1, wherein whenever said user logs in saidnetwork, said central server creates a status cookie storing said user'slogged-in status and sends said status cookie to said user's Webbrowser; wherein whenever said user switches from said any participatingwebsite to said any other participating website in a different domain,said user's Web browser sends said status cookie to said central server;and wherein said central server returns JavaScript to render said anyother participating website's toolbar in logged-in state if the cookiereceived is identical with said status cookie, or in logged-out state ifno cookie is received or the cookie received is not identical with saidstatus cookie.
 3. The method of claim 1, wherein said first toolbar andsaid another toolbar are substantially same.
 4. In a distributed singlelogin network which comprises at least one client, a plurality ofparticipating websites and a status indication server supporting avisual indicator embedded in each participating website, a method forautomatically displaying a Web user's authentication status, comprisingsteps of: said status indication server creating a status cookie storingsaid user's authentication status information when said user logs insaid network; sending said status cookie to said user's Web browser;said user's Web browser storing said status cookie; loading said visualindicator in logged-in state; when said user switches to any otherparticipating website, said user's Web browser sending said statuscookie to said status indication server; said status indication serverchecking whether said status cookie is received and whether the receivedcookie is valid; if a valid status cookie is received, returning a firstcode to said user's Web browser, said first code rendering said visualindicator in said any other participating website in logged-in state;and if said status cookie is missing or if the received cookie isinvalid, returning a second code to said user's Web browser, said secondcode rendering said visual indicator in said any other participatingwebsite in logged-out state; wherein each participating website embeds athird code which instructs said user's Web browser to load said firstcode or said second code from said status indication server.
 5. Themethod of claim 4, wherein said steps are performed in said orderrecited.
 6. The method of claim 4, wherein any of said codes isJavaScript.
 7. The method of claim 4, wherein said first code instructssaid user's Web browser to load an image which contains said user'spersonal identification information, wherein any of said participatingwebsites cannot understand the content of said image.
 8. The method ofclaim 4, wherein said visual indicator has only two states: logged-in;and logged-out.
 9. The method of claim 4, wherein said visual indicatormay vary in appearance in different participating sites.
 10. The methodof claim 4, further comprising the step of: any participating website insaid network recognizing a new visitor to said any participating websiteand displaying content customized to said net visitor.
 11. The method ofclaim 4, further comprising the step of: any participating website insaid network personalizing said website's user interface based on saiduser's status.
 12. The method of claim 4, further comprising the stepof: tracking users across multiple Web sites to determine theirinterests and to display customized content and promotions targeted tothe user.
 13. A distributed single login network comprising: a pluralityof participating websites with different domain names, a central statusindication server which hosts a process for displaying visual indicatorsof a user's status from site to site; and at least one client from whicha user logs in said network; wherein each of said participating websitesembeds a first JavaScript which instructs said user's Web browser toload from said status indication server a second JavaScript forrendering said visual indicator in logged-in state or a third JavaScriptfor rendering said visual indicator in logged-out state.
 14. The networkof claim 13, wherein when said user logs in said network, said statusindication server creates a status cookie which stores said user'sauthentication status information and sends said status cookie to saiduser's Web browser; wherein whenever said user switches from one toanother of said participating websites, said user's Web browser sendssaid status cookie to said status indication server; wherein if thecookie received is identical with said status cookie, said statusindication server returns to said user's Web browser said secondJavaScript for rendering said visual indicator in logged-in state; andwherein if the cookie received is not identical with said status cookie,said status indication server returns to said user's Web browser saidthird JavaScript for rendering said visual indicator in logged-outstate.
 15. The network of claim 13, wherein when said visual indicatoris in logged-in state, said visual indicator displays: said user's loginname or real name; and a first virtual button, by clicking which saiduser logs out said network.
 16. The network of claim 13, wherein whensaid visual indicator is in logged-out state, said visual indicatordisplays: a second virtual button, by clicking which said users isprompted to a login page; and a third virtual button, by clicking whichsaid user is prompt to a registration page.
 17. A method for displayinga Web user's authentication status in a distributed single loginnetwork, comprising the steps of: embedding bootstrapping code in atleast a first and a second web site which instructs said user's Webbrowser to load additional code from a central server hosting a processfor displaying visual indicators of a user's status from site to site,to render toolbars of said at least first and second web sites inlogged-in state or logged-out state; displaying said user's logged-instatus on a first visual indicator in a first website; when said userswitches from said first web site to said second web site, displayingsaid user's logged-in status on another visual indicator in said secondwebsite.
 18. The method of claim 17, wherein said first visual indicatorand said another visual indicator are substantially same.